Bahasa Rust: Peran Pengujian Otomatis dalam Rust

Di dunia Rust, kompiler adalah lini pertahanan pertama Anda, menangkap kebocoran memori dan ketidaksesuaian tipe sebelum terjadi. Namun, kompiler tidak dapat mengetahui tujuan Anda tujuan. Di sinilah Pengujian Otomatis masuk sebagai "jaring pengaman" untuk kebenaran logika.

1. Pasangan Pendukung

Sementara sistem tipe menangani integritas struktural, pengujian memverifikasi perilaku fungsional. Dalam sebuah proyek pustaka, kompiler memastikan Anda tidak melewatkan String ke fungsi matematika, tetapi hanya pengujian yang memastikan bahwa $f(x) = y$ menghasilkan hasil yang diharapkan.

2. Siklus Standar

Pengujian Rust mengikuti tiga langkah kaku:

Persiapan: Inisialisasi data (misalnya, membuat instans pustaka).
Jalankan: Jalankan logika spesifik yang sedang diselidiki.
Tegaskan: Verifikasi keadaan menggunakan makro seperti assert_eq!.

Toolchain terintegrasi mendukung Uji Dokumen (contoh yang dapat dijalankan dalam dokumentasi) dan Uji Benchmark untuk memastikan kode Anda tetap sangat cepat.

TERMINALbash — 80x24

> Ready. Click "Run" to execute.

QUESTION 1

Which attribute must be placed above a function to mark it as a test for the runner?

#[cfg(test)]

#[test]

#[verify]

#[cargo::test]

✅ Correct!

The #[test] attribute is the specific metadata that signals to the compiler to include the function in the test runner binary.

❌ Incorrect

While #[cfg(test)] is used for modules, individual functions require the #[test] attribute.

QUESTION 2

How does Rust primarily signal that a test has failed?

The function returns false.

The function executes a return Error;.

The function thread panics.

The compiler issues a warning.

❌ Incorrect

Rust tests look for panics to identify failure, though they can also return a Result.

QUESTION 3

Why is #[cfg(test)] used on the tests module?

To make the tests run faster.

To ensure tests are only compiled when running cargo test.

To allow the module to access private variables.

To export the tests to other crates.

QUESTION 4

Which command both compiles and executes the test runner binary?

cargo build --test

cargo test

rustc test.rs

cargo run tests

✅ Correct!

cargo test is the unified command that handles building the test binary and running it automatically.

❌ Incorrect

cargo build only compiles; cargo test is needed to execute the results.

QUESTION 5

What is the key difference between Doc-tests and Unit tests?

Doc-tests are only for documentation and cannot fail.

Unit tests live in code files; Doc-tests live inside triple-backtick comments.

Doc-tests are written in HTML, not Rust.

There is no difference.